Intelligent Watering System

ABSTRACT

A system may include a sensor disposed on a parcel of land, watering equipment comprising a watering pump and processing circuity, and a user terminal comprising a user interface. The sensor may be configured to detect moisture conditions. The processing circuitry may be configured to direct the watering pump to operate in accordance with an operational mode. The user terminal may be configured to output system information via the user interface based on sensor data provided by the sensor, control the watering pump to operate in accordance with the operational mode, and delegate operational control of the system to a second user in response to a delegation input provided by a first user via the user interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. application Ser.No. 16/092,131 filed on Oct. 8, 2018, which is a 371 U.S. National Stageentry of International application PCT/EP2016/057770, filed on Apr. 8,2016, all of which are hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

Example embodiments generally relate to intelligent systems and, moreparticularly, relate to a system for intelligent watering that includescomponents configured to facilitate easy interface and operation.

BACKGROUND

Grounds care maintenance tasks may include lawn care and/or gardeningtasks related to facilitating growth and manicuring the lawns or gardensthat hopefully prosper as a result of those efforts. Facilitating growthhas commonly required individuals to focus routine attention on ensuringgrowing conditions are appropriate for the vegetation being grown, andon providing the necessary care and grooming tasks to further enhancegrowth.

As technological capabilities have improved, various devices or sensorshave been developed that are capable of employment to monitor variousaspects of growing conditions. Gardeners have therefore been enabled toemploy the sensors or devices in specific locations to monitor andcorrect, if needed, the growing conditions. However, even with theimprovement of monitoring devices or sensors, gardeners are still oftenrequired to employ a high degree of manual interaction to place and/oroperate the devices or sensors.

WO 2009/049361 A1 describes a water resource management system thatemploys several sensors as well as a watering pump disposed on a parcelof land and being part of a communication network that allows distantcontrol via a common user terminal. The watering pump operates via anoperation mode in accordance to the command of the user terminal.

In case of connectivity losses in such a system the programmable logiccontroller of the automated irrigation system with US 2014/236868 A1will automatically force a reconnection of the deployed devices by areset of power so that these devices can recontinue to operate.

BRIEF SUMMARY OF SOME EXAMPLES

Some example embodiments may therefore provide a capability forintelligent control or management of a number of assets in connectionwith yard maintenance with the assistance or inclusion of a userterminal. Thus, for example, sensor equipment and watering equipmentoperation (with or without a robotic rover) may be coordinated remotelyfor efficient gardening and lawn care using a smart watering pump.

In an example embodiment, a system for intelligent control or managementof a number of assets in connection with yard maintenance is provided.The system may include sensor equipment including one or more sensorsdisposed on a parcel of land, watering equipment disposed on the parceland configured to selectively apply water to the parcel, and a gatewayconfigured to provide for communication with the sensor equipment andthe watering equipment. The watering equipment may include a wateringpump operably coupled to a water source and a water line to alternatelycouple the water source to and isolate the water source from the waterline, and processing circuitry. The processing circuitry may beconfigured to determine an operational mode of the watering pump; anddirect the watering pump to operate in accordance with the operationalmode.

In another example embodiment, a watering pump for intelligent controlor management of yard maintenance is provided. The watering pump may beoperably coupled to a water source and a water line to alternatelycouple the water source to and isolate the water source from the waterline, and may include processing circuitry. The processing circuitry maybe configured to determine an operational mode of the watering pump anddirect the watering pump to operate in accordance with the operationalmode.

Some example embodiments may improve the ability of operators tomaximize the beauty and productivity of their yards and gardens, but doso in a user friendly and intuitive way.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 illustrates a block diagram of a system in accordance with anexample embodiment;

FIG. 2 illustrates a block diagram of deployed components of the systemaccording to an example embodiment;

FIG. 3 illustrates a block diagram of processing circuitry that may beemployed in the deployed components according to an example embodiment;

FIG. 4 illustrates a block diagram of processing circuitry that may beemployed in a user terminal according to an example embodiment;

FIG. 5 illustrates a flow diagram of various operations associated withcontrol of a watering pump in accordance with an example embodiment; and

FIG. 6, which includes FIGS. 6A, 6B, and 6C, illustrates exampleinterface consoles or screens that may be generated at the user terminalaccording to an example embodiment.

DETAILED DESCRIPTION

Some example embodiments now will be described more fully hereinafterwith reference to the accompanying drawings, in which some, but not allexample embodiments are shown. Indeed, the examples described andpictured herein should not be construed as being limiting as to thescope, applicability or configuration of the present disclosure. Rather,these example embodiments are provided so that this disclosure willsatisfy applicable legal requirements. Like reference numerals refer tolike elements throughout. Furthermore, as used herein, the term “or” isto be interpreted as a logical operator that results in true wheneverone or more of its operands are true. Additionally, the term “yardmaintenance” is meant to relate to any outdoor grounds improvement ormaintenance related activity and need not specifically apply toactivities directly tied to grass, turf or sod care. Thus, yardmaintenance should be appreciated to encompass gardening, lawn care,combinations thereof, and/or the like. As used herein, operable couplingshould be understood to relate to direct or indirect connection that, ineither case, enables functional interconnection of components that areoperably coupled to each other.

Example embodiments may provide an intelligent system for monitoringand/or maintaining yard conditions (i.e., lawn and/or garden conditions)at any of what may potentially be a number of locations throughout aparticular parcel, and allowing the operator to interface with deviceswithin the system in a flexible way. Moreover, the devices of the systemmay be coordinated in their activities and/or may be configured to adaptto their environment or at least to the current conditions or stimulithat are present in their environment. In some cases, the operationsconducted and/or monitoring may be accomplished with the assistance of amobile asset such as a robotic rover. In this regard, for example, thesystem may utilize a communication network that gathers information ongrowing conditions from sensor equipment for association of theinformation with the areas from which the information was gathered. Thesystem may also employ an interface mechanism that allows the operatorto have a great deal of flexibility with remotely controlling variouscomponents of the system and programming such components via processingcircuitry at each respective component. Programming may therefore becoordinated remotely, but at least some of the programming may also bestored locally so that the system can operate with or withoutconnectivity. In some cases, the connectivity aspects of the system mayutilize home network components and wide area network components (e.g.,the internet), but may also include a gateway that is configured tointerface between the deployed components (e.g., components in theyard/garden or otherwise related to yard maintenance) and the homenetwork/wide area network components. As mentioned above, the processingaspects may be distributed between local and remote managementcomponents so that some aspects of yard maintenance may utilize remoteassets or at least incorporate information available from abroad, whileother aspects can be managed locally. In any case, adaptability and easeof interface and control are characteristics of the system that areimproved by employing example embodiments.

The system may therefore employ any combination of fixed and/or mobileassets that gather data that relates to specific segments of the parcelthat may correspond to respective different areas. In particular, thesystem may employ an intelligent watering pump that is configured to beprogrammed for servicing one or more such specific segments. Thespecific segments may have different types of plants therein, andtherefore may optimally have different growing conditions desirable inconnection with each respective one of the segments. The owner/operatormay program operating instructions to guide the deployed components(including the intelligent watering pump) relative to operations in oneor more of the specific segments, which may be referred to as “zones.”In some cases, the processing circuitry may be equipped to allow theuser to define specific operating parameters and the system may thenadapt to the current conditions to operate according to the operatingparameters. Given that internet connectivity is possible, in some cases,the system may be employed to correlate desirable growing conditions toan identified plant species based on stored information associated witheach plant species from a database or online resource. Accordingly, eachzone may have corresponding growing condition parameters associatedtherewith, and the user can see the growing condition parametersrelative to the various areas and program operation of system componentsaccordingly relative to maintaining desired growing conditions (e.g.,any or all of moisture level, temperature, lighting level, pH, and/orthe like) for the corresponding zone. In some cases, schedules amongdeployed components may be deconflicted or otherwise organized toprevent damage to components, ineffective use of resources, orefficiency reducing behaviors. The deployed components associated withthe zones may provide the operator with reports and/or warnings via thegateway to enable the operator to intercede in certain situations, orthe components may simply respond and inform the operator of theirresponses via the gateway.

FIG. 1 illustrates a block diagram of a system 10 that may be employedto accomplish the basic operations described above in accordance with anexample embodiment. Within the context of FIG. 1, it should beappreciated that certain tasks, like grass cutting, chemicalapplication, visual monitoring and/or the like may be performed by arobot or robotic rover 15. Because the system could operate without therobotic rover 15, the robotic rover 15 is shown in dashed lines inFIG. 1. Robots or other devices could also be engaged to perform certainother yard maintenance tasks such as raking, fertilizing, lighting,wildlife dispersion and/or the like.

Other tasks, like lawn watering, may be performed bysprinkler/irrigation heads and/or a watering pump that interfacestherewith. The sprinkler/irrigation heads may be attached to hoses andthe watering pump may provide a mechanism by which to control theturning on/off of water application at the respectivesprinkler/irrigation head locations by providing a central intelligentlycontrollable source for providing water to the sprinkler/irrigationheads and/or the hoses. The hoses, sprinkler/irrigation heads, and/orwatering pump may together form watering equipment 20.

Meanwhile, various sensors may be employed by insertion of such sensorsinto soil for monitoring soil or other growing conditions (e.g.,lighting levels, moisture levels, pH, temperature, video or image data,etc.). These sensors may therefore be understood to take various formswithin the system 10. However, generally speaking, the sensors may haveconnectivity to the system 10 in order to enhance operation of systemcomponents on the basis of the soil and/or growing condition informationgathered by the sensors. Regardless of the specific configuration orplacement paradigm, the various sensors may represent sensor equipment30, as described above.

The sensor equipment 30, and in some cases also one or more of thedevices that comprise the watering equipment 20, may be in communicationwith a gateway 40 via wired or wireless connections. The gateway 40 maysubsequently have wired or wireless connection to an access point (AP)45, which may be directly or indirectly connectable to a user terminal50. The AP 45 may be a router of a home network of the operator. In somecases, direct connection of the AP 45 to the user terminal 50 may beprovided via short range wireless communication methods (e.g.,Bluetooth, WiFi and/or the like). Indirect connection of the AP 45 tothe user terminal 50 may occur via a network 60. The network 60 may be adata network, such as a local area network (LAN), a metropolitan areanetwork (MAN), a wide area network (WAN) (e.g., the internet), awireless personal area network (WPAN), and/or the like, which may coupledevices (e.g., the deployed components) to devices such as processingelements (e.g., personal computers, server computers or the like) and/ordatabases such as the user terminal 50. Communication between thenetwork 60 and other devices of the system 10 may be accomplished byeither wireline or wireless communication mechanisms and correspondingcommunication protocols. As such, for example, some or all of thesensors of the sensor equipment 30, the watering equipment 20 and/or therobotic rover 15, may be connected to the user terminal 50 by wireand/or be wireless communication means.

It should also be appreciated that although the robotic rover 15 isillustrated separately in FIG. 1, the robotic rover 15 may act as one orboth of a piece of sensor equipment 30 or a piece of watering equipment20. However, given the ability of the robotic rover 15 to act as eitheror both of a piece of sensor equipment 30 or a piece of wateringequipment 20 and the ability of the robotic rover 15 to perform othertasks (e.g., grass cutting) in combination with or independent of thesensor equipment 30 and the watering equipment 20, the robotic rover 15is shown separately in FIG. 1.

The gateway 40 may be a translation agent configured to interface withany or all of the deployed components via wired or wirelesscommunication. In some embodiments, the gateway 40 may include a highperformance antenna to enable the gateway 40 to communicate wirelesslywith deployed components via an 868 mHz radio link (e.g., a firstwireless link). However, other radio links may be employed in othercases. The first wireless link, and the components connected thereby,may be part of a first network (e.g., a garden network) or deployedcomponent network that extends outdoors. Components internal to thehouse or business, and extending to and between the user terminal 50 mayform a second network. As such, the gateway 40 may be a translationagent between the first and second networks. The gateway 40 may be anaggregation point and communications center for communications in bothnetworks.

As such, the gateway 40 may be provided within the home or otherwiseindoor environment of the operator, and still wirelessly communicatewith the deployed components (via the first wireless link) to translateinstructions thereto from the operator, which may be provided via asecond wireless link to the AP 45. In an example embodiment, thewireless communications may be secured by employing encryption or othersecurity techniques. The gateway 40 may also provide secure cloud datastorage through connection to the network 60 (e.g., via the AP 45). Insome examples, the first and second wireless links may be differentwireless links that employ different communication protocols and/orfrequencies.

The gateway 40 may also provide the ability for each of the deployedcomponents to be monitored, controlled, programmed, or otherwiseinterfaced with by an operator using the user terminal 50. Inparticular, in some cases, the user terminal 50 may be configured toexecute an application (or app) that is tailored to providing an easysetup and/or easy to use interface for interaction with the gateway 40(and the corresponding deployed components that are reachable throughthe gateway 40). The user terminal 50 may therefore be a smartphone orother mobile terminal, or a laptop, PC, or other computing/communicationdevice. As such, the user terminal 50 may include processing circuitrythat is enabled to interface with corresponding processing circuitry ofthe gateway 40 and/or the deployed components to program, control orotherwise interact with the deployed components in a manner described ingreater detail below.

The interaction between the user terminal 50 and the gateway 40 tofacilitate programming of, control of, or interaction with the deployedcomponents may create an interactive and fully connectable garden systemfor irrigation or mowing control/coordination. The app that may beexecuted at the user terminal 50 may be configured for control of any orall of the deployed components on a real time or programmed basis. Theresulting system may be a holistic and connected automatic gardensystem. Moreover, the connection to content on the internet via network60 may allow educational content to be integrated into the system'soperation to provide operators with an improved interface and morecontrol over gaining full satisfaction of their gardening experience.For example, the educational content may include videos that example howto start, program, or troubleshoot any operations regarding thecomponents of the water equipment 20. In an example embodiment, the appmay be used to program at least some of the watering equipment 20 tooperate on a locally stored watering schedule in a first mode andoperate as an autonomous pressure pump in a second mode of operation.

FIG. 2 illustrates a water migration path that may be practiced inconnection with an example embodiment. However, it should be appreciatedthat some of the components may be removed in simpler exampleembodiments, and some components may be added to provide more complexarchitectures in other example embodiments. Thus, the example of FIG. 2is not provided to be limiting in relation to the components included inthe system, but merely to show an example of some components that may beincluded in one example system. Moreover, it should be appreciated thatalthough FIG. 2 shows a single water delivery line, other embodimentscan employ multiple water delivery lines to service a parcel or yard.Thus, example embodiments may be practiced with any number of lines, andwith separate and/or different water sources.

Referring now to FIG. 2, a water source 100 may be used to charge awater line 110 via a watering pump 120. In some cases, the water source100 may also charge a second water line via a second watering pump, orvia the first watering pump 120. The water line 110 may be a flexiblewater hose or garden hose. The watering pump 120 may be one of thedeployed components that forms one component of the watering equipment20 of FIG. 1. The watering pump 120 may be operably coupled to the watersource 100 such that the water source 100 is a pressurized water supplyfor the water line 110 when the watering pump 120 is operational.However, when the watering pump 120 is not operational, the water line110 may be substantially depressurized, or at least only have residualpressure remaining from the last operation of the watering pump 120.Thus, it should be understood that the water source 100 is not a typicalpressurized water supply of a house or other structure. Instead, thewater source 100 may typically be an otherwise unpressurized watersource, such as a reservoir or cistern.

In an example embodiment, one or more sprinklers (e.g., a firstsprinkler 130 and a second sprinkler 132) may receive water from thewater line 110. The water line 110 may be selectively charged undercontrol of the watering pump 120 to provide water for spraying from thefirst and second sprinklers 130 and 132. Likewise, if used, the secondwater line may be selectively charged under control of the watering pump120, or a second watering pump, to provide water for spraying from anyadditional sprinklers associated with the second water line. When thewater line 110 is charged, the first and second sprinklers 130 may beprovided with pressurized water that is distributed therethoughresponsive to operation of the watering pump 120. The first and secondsprinklers 130 and 132 may typically be components that are not providedwith any local intelligence. Instead, the first and second sprinklers130 and 132 may only be controllable via operation of the watering pump120 to turn on and off watering functions. However, it is possible thatthe first and second sprinklers 130 and 132 could have intelligentcomponents and/or control aspects provided therein in some cases.

One or more sensors (e.g., first sensor 140 and second sensor 142) mayalso be provided at various locations in the parcel that is served bythe sprinklers to detect or sense conditions proximate to thecorresponding sensors. The first and second sensors 140 and 142 may eachcorrespond to a respective one of the first and second sprinklers 130and 132, and the app at the user terminal 50 may be configured to notesuch correspondence so that information received from a respective oneof the first or second sensor 140 or 142 can be correlated to actionsthat may be ordered to the watering pump 120, if needed, based on theinformation.

In some examples, some of the deployed components may include a powersupply (P/S) 150 that is local to the corresponding ones of the deployedcomponents. The P/S 150 of each component may be a battery or batterypack, or mains power. Each powered one of the deployed components mayalso include communication circuitry (C/C) 160 that includes processingcircuitry for controlling each respective component and an antenna forenabling the deployed components to communicate with the gateway 40 viathe first wireless link (or alternatively via a wired connection). Therobotic rover 15 (if employed) may also be an example of the deployedcomponents, and thus the robotic rover 15 may also include the P/S 150and the C/C 160. However, it should be appreciated that the variouspower supply and communication circuitry components may have differentscale, structure and configuration features.

The watering pump 120 may generally operate under the control of the C/C160 to respectively isolate and operably couple the water source 100from/to the water line 110. The watering pump 120 may operate based onoperational and volume mode instructions received through the gateway 40or based on operational and volume information stored or otherwiseaccessible via the C/C 160 of the watering pump 120. The watering pump120 may provide convenience to operation of the system 10 since thewatering pump 120 can be controlled from anywhere and/or at anytime viathe app at the user terminal 50, or via locally stored programminginstructions, by selecting or executing the desired/programmedoperational and volume mode, as described in greater detail below.

In an example embodiment, the C/C 160 may include processing circuitry201, as shown in FIG. 3. The processing circuitry 201 that may beconfigured to perform data processing, control function execution,and/or other processing and management services according to an exampleembodiment of the present invention. In some embodiments, the processingcircuitry 201 may be embodied as a chip or chip set. In other words, theprocessing circuitry 201 may comprise one or more physical packages(e.g., chips) including materials, components and/or wires on astructural assembly (e.g., a baseboard). The structural assembly mayprovide physical strength, conservation of size, and/or limitation ofelectrical interaction for component circuitry included thereon. Theprocessing circuitry 201 may therefore, in some cases, be configured toimplement an embodiment of the present invention on a single chip or asa single “system on a chip.” As such, in some cases, a chip or chipsetmay constitute means for performing one or more operations for providingthe functionalities described herein.

In an example embodiment, the processing circuitry 201 may include oneor more instances of a processor 205 and memory 203 that may be incommunication with or otherwise control a device interface 207. As such,the processing circuitry 201 may be embodied as a circuit chip (e.g., anintegrated circuit chip) configured (e.g., with hardware, software or acombination of hardware and software) to perform operations describedherein. In some embodiments, the processing circuitry 201 maycommunicate with internal electronic components of the watering pump120, the first or second sensors 140 and 142 and/or the robotic rover15, and enable communication externally with other components.

The device interface 207 may include one or more interface mechanismsfor enabling communication with other devices via the gateway 40. Insome cases, the device interface 207 may be any means such as a deviceor circuitry embodied in either hardware, or a combination of hardwareand software that is configured to receive and/or transmit data from/tothe gateway 40 by virtue of the device interface 207 being capable ofsending and receiving messages via the gateway 40. In some exampleembodiments, the device interface 207 may provide interfaces forcommunication of components of or external to the system 10 via thegateway 40. If the C/C 160 is for a sensor, the device interface 207 mayfurther interface with a sensor (e.g., a temperature sensor, a pHsensor, a light sensor, a moisture sensor and/or the like) to obtainsensor data for communication to other devices (e.g., the wateringpump(s)). Meanwhile, if the C/C 160 is for a watering pump, the deviceinterface 207 may provide interfaces to other onboard components (e.g.,a user interface including lights and a main button as described below).

The processor 205 may be embodied in a number of different ways. Forexample, the processor 205 may be embodied as various processing meanssuch as one or more of a microprocessor or other processing element, acoprocessor, a controller or various other computing or processingdevices including integrated circuits such as, for example, an ASIC(application specific integrated circuit), an FPGA (field programmablegate array), or the like. In an example embodiment, the processor 205may be configured to execute instructions stored in the memory 203 orotherwise accessible to the processor 205. As such, whether configuredby hardware or by a combination of hardware and software, the processor205 may represent an entity (e.g., physically embodied in circuitry—inthe form of processing circuitry 201) capable of performing operationsaccording to embodiments of the present invention while configuredaccordingly. Thus, for example, when the processor 205 is embodied as anASIC, FPGA or the like, the processor 205 may be specifically configuredhardware for conducting the operations described herein. Alternatively,as another example, when the processor 205 is embodied as an executor ofsoftware instructions, the instructions may specifically configure theprocessor 205 to perform the operations described herein.

In an example embodiment, the processor 205 (or the processing circuitry201) may be embodied as, include or otherwise control the C/C 160. Assuch, in some embodiments, the processor 205 (or the processingcircuitry 201) may be said to cause each of the operations described inconnection with the C/C 160 (and corresponding distributed componentwith which the C/C 160 is associated) by directing the C/C 160 toundertake the corresponding functionalities responsive to execution ofinstructions or algorithms configuring the processor 205 (or processingcircuitry 201) accordingly. As an example, the C/C 160 of the sensorsmay be configured to detect environmental parameters (e.g., sensor data)and report the sensor data via the first wireless link to the gateway 40(and ultimately to the app on the user terminal 50 or to storage in thecloud via the network 60) or to the watering pump 120. In some cases,the C/C 160 of the sensors may be configured to determine a differencebetween a prior set of sensor data (e.g., the magnitude of a previoussensor measurement) and the current set of sensor data (e.g., themagnitude of a most recent sensor measurement). The amount of differencemay then be used to determine whether or not the sensor will report thecurrent set of sensor data. If the difference is small (e.g., less thana threshold amount) the sensor may not report the new value. However, ifthe difference is large enough (e.g., larger than the threshold amount),then the sensor may report the new value. As such, the C/C 160 of thesensors may be configured to perform battery conservation techniquesrelative to reporting of sensor data. The C/C 160 of the sensors mayalso be configured to otherwise report (or make a determination onwhether to report based on the criteria discussed above) sensor data ona given schedule or responsive to certain activities or events. When atrigger event (e.g., temporal or action based trigger) occurs, the C/C160 of the sensor may make a determination of the current sensor dataand decide whether or not to report the sensor data.

The C/C 160 of the watering pump 120 may be configured to receiveinstructions from the gateway 30 regarding an operational mode of thewatering pump 120 as defined by the app, or by locally storedprogramming. For example, the gateway 40 may receive instructions fromthe user via the user terminal 50 regarding what operational mode (e.g.,controlling on/off cycles of the pump) the user desires the wateringpump 120 to operate in. In some example embodiments, the user-selectableoperational modes of the watering pump 120 may include, but are notlimited to, an intelligent mode, a scheduled mode, or a manual mode.When the intelligent mode is selected by the user, the watering pump 120may operate independently based on programmed triggers. In some cases,the triggers may be sensor data received from the first or second sensor140 or 142. For example, the C/C 160 of the watering pump 120 may beprogrammed to turn on the watering pump 120 and provide water whensensor data falling within or exceeding certain ranges or thresholds isreceived. Thus, in some example embodiments, if the sensor dataindicates that soil moisture is below a given threshold, the wateringpump 120 may be configured to energize the watering pump 120 to enabledelivery of water to the sprinklers.

When the scheduled mode is selected by the user, the operator may selecta schedule on which the watering pump 120 may operate. For example, theuser may select certain times or days in which the watering pump 120should operate. If the manual mode is selected by the user, the wateringpump 120 may only operate upon the user selecting an option on the userterminal 50 that directs the operation of the watering pump 120.Therefore, the user at any time may decide to water the lawn and maydirect the watering pump 120, via the user terminal 50, to operate. Insome cases, the user may select more than one operational mode at atime. For example, the user may send instructions, via the gateway 40,to the watering pump 120 regarding a schedule on which the watering pump120 is to operate. However, in addition to this provided schedule, theuser may instruct the watering pump 120 to also simultaneously act inthe intelligent mode. For example, the user may define triggers underwhich the watering pump 120 may operate. These triggers may include, butare not limited to, the soil moisture falling below or exceeding a giventhreshold. Accordingly, the watering pump 120, via the C/C 160, may beconfigured to operate on a schedule while also operating in response topre-defined triggers. Even if the user has selected that the wateringpump 120 is to operate under both the intelligent and scheduled mode,the user may select the manual operation mode which causes the wateringpump 120 to operate whenever the user desires. The user may select thismanual operation mode without affecting the already programmedintelligent and scheduled modes.

Even further, the C/C 160 of the watering pump 120 may be configured toreceive instructions from the user (via the gateway 40) regarding avolume mode of the watering pump 120. Therefore, the gateway 40 mayreceive instructions from the user via the user terminal 50 regardingnot only what operational mode (e.g., on/off cycle control) the userdesires the watering pump 120 to operate in, but what volume mode thewatering pump 120 should operate in where the volume mode defines pumpspeed or output pressure. The volume modes of the watering pump 120 thatmay be selectable by the user include, but are not limited to, 1) microdrip mode; 2) small amount mode; 3) conservation mode; 4) automaticmode; or 5) garden mode. The micro drip mode, for example, may supply asmall amount of water at a gentle drip or trickle pressure. The user mayselect the micro drip mode for irrigating or watering flowers orvegetation. The small amount mode may be suitable for when only a smallarea is being irrigating or watered. The conservation mode may ensurethat the watering pump 120 is not operational while a shower, washingmachine, dish washer, or the like is being operated in the houseassociated with the parcel to ensure sufficient water pressure ismaintained both in the home and at the watering pump 120. The automaticmode may allow the C/C 160 of the watering pump 120 to determine theappropriate volume of water to be supplied by the watering pump 120based on the on sensor data received from the first or second sensor 140or 142. The garden mode may be selected when a full soaking of thegarden, lawn, or flower bed is desired and full pump or line pressure isdesired.

In some cases, the volume modes may be selectable based on certain areasof the lawn or parcel. Even further, some of the volume modes may beselectable simultaneously. For example, the user, via the user terminal50, may select that the garden mode should be employed on Saturday at8:00 a.m. for zone 1 of the parcel. In conjunction with selecting thegarden mode for the applicable time period for zone 1, the user may alsoselect the conservation mode. Therefore, if the washing machine isrunning at 8:00 a.m. on Saturday morning, the C/C 160 may be configuredto delay the operation of the watering pump 120 in garden mode untilthere is detection that the washing machine has shut-off or until apreset time delay expires. In other cases, the user may be alerted, viathe user terminal 50, that the garden mode was not implemented due thedetection of the washing machine being operated. Upon receiving thisalert, the user may override the conservation mode and implement thegarden mode, or in some cases, the user may select when the garden modeshould be rescheduled.

In some example embodiments, the last received instructions regardingthe operational or volume mode from the user may be stored locally inthe memory 203 of the C/C 160. Accordingly, if the C/C 160 losesconnectivity to the gateway 40, the C/C 160 may continue to employ thelast received instructions regarding the operational or volume mode ofthe watering pump 120. In another example embodiment, if the C/C 160loses connectivity to the gateway 40 or loses connectivity for longerthan a predetermined time period, the C/C 160 may be configured tooverride the last received instructions from the user regarding theselected operational or volume mode and switch to a default setting. Insome cases, the default setting may the intelligent operational mode orthe automatic volume mode. Therefore, the C/C 160 will determine theappropriate time to water and the appropriate volume of water to besupplied by the watering pump 120 based on sensor data received from thefirst or second sensor 140 or 142. In either case, the default settingsor the last received instructions (and any programs associatedtherewith) are stored locally at the C/C 160 so that the watering pump120 can operate independently of connectivity to the network 60.

The C/C 160 of the robotic rover 15 may be configured to control thetravels and operations of the robotic rover 15. Moreover, the C/C 160 ofthe robotic rover 15 may allow the gateway 40 to grant user access tomodification of the schedule of operations of the robotic rover 15and/or to take real-time control over various operations of the roboticrover 15. In an example embodiment, the app at the user terminal 50 maybe employed to coordinate and/or de-conflict programmed water schedulesand mowing schedules. Additionally or alternatively, if the operatormakes a modification to a operational mode of the watering pump 120 ortakes manual control of one or more components, the app at the userterminal 50 may provide alerts to indicate that the proposed changes tothe schedule or current operational mode may be problematic, or mayprevent the making of such changes. Thus, for example, if the roboticrover 15 is mowing in an area in which a sensor indicates a low soilmoisture value that would normally trigger operation of the wateringpump 120 via the programming of the watering pump 120, an alert may beprovided to indicate that the robotic rover 15 should have itsoperations changed, or the opening of the watering pump 120 may bedelayed.

In an example embodiment, the electronic deployed components (e.g.,components having a P/S 150) may further include a local operator 211(e.g., a button, knob or other control device) provided at a portionthereof. In some cases, the local operator 211 may be provided to allowlocal manual setting of one or more characteristics of the watering pump120. Thus, for example, the local operator 211 may be used to determinepump output pressure, speed, volume mode, operational mode, and/or thelike. The local operator 211 may trigger different functionalitiesthrough the programming of the processing circuitry 201 forcorresponding different situations and/or actuation methods. Forexample, some actuation of the local operator 211 may cause thecorresponding device to go into a pairing mode. Once in the pairingmode, the device may be detectable by the gateway 40 and/or otherdevices for a given period of time. The app on the user terminal 50 maybe used to detect the device in pairing mode and, once detected, the appmay also be used to pair the device to another device (e.g., of thefirst network—the deployed component network). The gateway 40 and theC/C 160 of the corresponding devices may then be capable ofcommunication with each other on a continuous, event driven, orscheduled basis via the first wireless link. Thus, for example, thefirst sensor 140 may be configured to provide sensor data to thewatering pump 120 (e.g., via the gateway 40). In some cases, the firstsensor 140 may be paired with the watering pump 120 via a setupprocedure and communicate thereafter on a schedule or an activity/eventdriven basis. In some cases, simple replacement or insertion of abattery to power up the device may be an additional or alternativemethod by which to initiate the pairing mode.

In some cases, certain defined actuation (or patterns of actuation) ofthe local operator 211 may result in returning the device to factorysettings. As such, contents of the memory 203 may be cleared orotherwise reset to initial settings or conditions. Other functions mayalso or alternatively be provided. Moreover, some devices may haveadditional buttons or operable members.

Communication between the gateway 40 and the sensors or watering pumpsmay occur for pairing purposes and to facilitate the operationalactivities for which the system 10 is ultimately configured. Thus, forexample, the operator may use the app at the user terminal 50 to connectto the gateway 40 and may be provided with one or more control consoleor interface screens that provide options for interacting with deployedcomponents and/or for programming the deployed components, as describedabove. In some cases, initial setup of the system may be facilitated byplacing individual deployed components (either sequentially orsimultaneously) in a pairing mode. The deployed components are thendiscoverable via the first wireless link and can be added to the firstnetwork. Once added to the first network, the deployed components areconsidered to be assets of the first network that can be interactedwith/programmed and/or the like. The deployed components can then bepaired with each other and configured for individual and/or cooperativefunctional performance.

In an example embodiment the watering pump 120 may be paired with othersecond watering pumps, with the robotic rover 15 and/or the first sensor140. When the watering pump 120 is paired with and connected to thefirst sensor 140, the operator may have options provided (e.g., via theapp) to select the desired operational or volume mode of the wateringpump 120. In cases where the intelligent operational mode is selected bythe user, the watering pump 120 may therefore be instructed regardingthe specific stimuli that may be received from the first sensor 140 totrigger operation of the watering pump 120. However, as described above,the watering pump 120 may be provided with (e.g., in the memory 203) aschedule or a trigger which causes the watering pump 120 to “ping” orotherwise reach out to the first sensor 140 to initiate communication toreceive sensor data. Based on the sensor data received (e.g., if certainthreshold parameters are reached or not), the watering pump 120 may beopened or closed.

When the watering pump 120 is paired with and connected to the roboticrover 15, automatic coordination of schedules may be accomplished atleast relative to ensuring that mowing and watering are not conducted inthe same area at the same time. The app on the user terminal 50 mayensure that scheduling of mowing during watering (or vice versa) is notpossible. However, given that the operator can take control of thewatering pumps and/or the robotic rover 15 to initiate operations, theapp on the user terminal 50 may further prevent any attempts to initiateoperations of watering pumps or the robotic rover 15 in real-time whenthe other is also operating in the same area.

When the watering pump 120 is paired with and connected to otherwatering pumps, watering schedules or operations can be coordinated tomanage or prevent under-pressure situations or excessive draining of thewater source 100. For example, if the watering pumps are connected tothe same water source, it may be possible for water supply to beinsufficient to effectively charge both the water line 110 and thesecond water line at the same time. Thus, by allowing multiple wateringpumps to be in communication with each other, operations of one may becommunicated to the other (e.g., via the gateway 40) so that the watersource 100 and its supply of water can be managed effectively.

Therefore, the deployed components of various example embodiments may beadaptive to various conditions or situations. Moreover, the adaptivenature of the deployed components may be provided, as described above,as a programmable feature, where the operator can use the user terminal50 to program modes, adjustable parameters, relationships, or responses.In the context of some examples, the programmable features should beunderstood to be remotely programmable (i.e., programmable from the appand/or the user terminal 50 remote from the component being programmed)via the gateway 40. In other examples, the adaptive nature of thedeployed components may be provided as a default feature. Thus, theadaptive capabilities of the deployed components may either be dependentupon connectivity (e.g., connectivity dependent) for remote programming,or may be connectivity independent (e.g., default programming thatexists or is instituted when there is no connectivity or responsive to aloss of connectivity.

In some embodiments, battery power levels may be communicated to thegateway 40 and signal strength values relating to communication with thesensors and/or watering pumps may also be determined at the gateway 40.This information (along with sensor data) may be provided to the app atthe user terminal 50 to alert the operator when battery power is low, orsignal strengths are low. Battery replacement and/or sensorrepositioning may then be undertaken to improve the situation. Asmentioned above, in some cases, the sensor may also adaptively respondto its surroundings to trigger reports. In an example embodiment, thewatering pump 120 may attempt to ping the first sensor 140 via thegateway 40 to trigger a report of sensor data. However, the first sensor140 may be configured (e.g., via the C/C 160) to determine the amount ofchange in the requested parameter before deciding whether to respond tothe ping. In some embodiments, a change of at least a specific amount orpercentage (e.g., 5%) may be required before the first sensor 140 willreport sensor data via wireless transmission. Since wirelesstransmission consumes more power than internal operation (e.g., todetermine the amount of change and current sensor data), by savingseveral transmission cycles when there is little data change, batterylife can be substantially extended. When a ping is sent and no responseis received, the last value received may be substituted and communicatedto the operator (e.g., via the app).

The operator can turn on/off or wake up the watering pumps and/orsensors by sending instructions via the user terminal 50 through thegateway 40. For example, the wake up message may be used to see if thedevices are still reacting and active, or to request specific data fromor initiate actions at such components in real time. Moreover, in somecases, the operator can send a wakeup, or setup signal to have thecorresponding device beacon for at least a predetermined amount of time(e.g., three minutes). During this time, the devices may be positionedand the operator may check the app to see what signal strength isdetected by the gateway 40. The operator can therefore position thedevices in real time and make sure that the position in which a deviceis currently located is a good location from the perspective of itsability to communicate with the gateway 40.

In some embodiments, one or more of the deployed components may furtherinclude frost warning capability. In particular, since the wateringpumps typically may have some residual water therein, it should beappreciated that freezing of water in the body of the watering pumps maybe destructive to the watering pumps. Accordingly, the C/C 160 of one ormore components (especially the watering pumps) may be configured toidentify situations where there is a potential for frost that may damagethe watering pumps or other watering equipment 20. In some embodiments,if the temperature reaches a predetermined threshold distance from thefreezing point (e.g., 5 degrees C., or 10 degrees F.), an alert may beissued (e.g., through the app at the user terminal 50) to warn theoperator that the watering pump 120 (and/or sensors) should be broughtin to avoid damage. The predetermined threshold may be a factorysetting, or may be set by the operator. However, in either case, theability to identify a present temperature condition to alert theoperator of a possible frost event is another example of how thedeployed components may be configured (by operator program or bydefault) to be adaptive relative to their surroundings and/orcircumstances.

Another example of the adaptability of the deployed components relatesto the inability to connect to the first network or a loss of connectionto the first network. For example, although the last received operationor volume mode could be maintained in the cloud, on the user terminal50, or elsewhere, in some cases, the current operational or volume mode(or at least a portion thereof) may be stored locally at the wateringpumps. For example, the memory 203 may be configured to record at leastthe last water schedule information employed. Thus, if power is lost atthe gateway 40 or at another system component that thereby rendersconnectivity impossible, the watering pump 120 may store at least theinformation indicative of its last watering schedule. Thus, for example,if the watering pump 120 operated at 1300 and shut down at 1305, if noconnection to the network 60 for determining the watering schedule canbe achieved, or if connectivity is lost, the watering pump 120 willcontinue to water on the previously provided operational and volumemode. In some cases, if the C/C 160 of the watering pump 120 determinesthat connectivity has been lost for longer than a pre-determined timeinterval, the C/C 160 may be configured to override the previouslyprovided operational and volume mode to operate on the default setting,as described above.

In further example embodiments, C/C 160 of the deployed components mayable to determine the usage and runtime of each of the deployedcomponents. For example, the C/C 160 may be configured to monitor andcalculate the runtime of and the water usage by the watering pump 120.Therefore, the C/C 160 may be able to determine the volume of water usedover a specific time interval, such as an hour, day, week, month, orplurality of months (i.e., seasons). These calculations may be providedto the user via the user terminal 50. Based on the calculations, the C/C160 may determine an average runtime and usage of the watering pump 120over a pre-determined time interval. Using these calculated averageruntime and usage values, the C/C 160 may be configured to monitor anyfurther usage and runtime of the watering pump 120. If the runtime orusage exceeds the average runtime and usage values, the C/C 160 may beconfigured to send an alert, via the gateway 40, to the user terminal 50to indicate the status detection of the abnormal condition.

An even further example of the adaptability of the deployed componentsrelates to the ability of the C/C of the deployed components todetermine the recommended maintenance interval for the deployedcomponents. For example, using the above calculated average runtime andusage of the watering pump 120over a predetermined time period, the C/C160 of the watering pump 120 may be able to calculate the recommendedmaintenance interval of the watering pump 120. This recommendedmaintenance interval may be displayed on the user terminal 50. In someexample embodiments, the user may be able to override this recommendedmaintenance interval. The user may be able to select how he or she wantsto calculate the maintenance interval (i.e., after a certain time periodor certain calculated usage amount). In that case, the C/C 160 may beconfigured to alert the user when the time period has passed or when thespecified usage amount occurs. Even further, the user may be able toinput when the last maintenance was performed on the watering pump 120.By inputting the last maintenance performed, the C/C 160 may beconfigured reset the maintenance interval and recalculate in accordancewith the above.

In some example embodiments, the C/C 160 of the deployed components maybe even further configured to send messages to the user that operationof the deployed component has started. In other cases, the C/C 160 maybe configured to send messages if the deployed component fails duringoperation or if an error occurs during operation. If a failure or erroroccurs during the operation of the deployed component, the user terminal50 may have an option to for the user to send feedback to themanufacturer or supplier of the error or failure. In even furtherexample embodiments, the user terminal 50 may be configured to allow themanufacturer or supplier to have remote access of the deployablecomponent in response to receiving a request from a user or in responseto receiving feedback regarding the failure or error of the deployablecomponent.

The watering pump 120described above could take different physicalforms. However, an example structure for embodying a watering pump 120may be a reciprocating or rotary pump. Thus, for example, the wateringpump 120 may include a centrifugal pump having an impeller. However,other pump structures can also be employed.

As has been noted above, the deployed components (e.g. the watering pump120) may be largely controlled by the user via the user terminal 50. Asmentioned above, the user terminal 50 could be a mobile device (e.g., asmartphone) or a fixed terminal (e.g., a PC). However, the user terminal50 could also be other devices such as a tablet, laptop and/or the like.In any case, the user terminal 50 may be configured to provide a simpleand intuitive interface for enabling the operator to control operationof the system 10. FIG. 4 illustrates a block diagram of some componentsof the user terminal 50 that may configure the user terminal to providethe app for control of the system 10.

As shown in FIG. 4, the user terminal 50 may include processingcircuitry 310, a processor 312, memory 314 and device interface 320 thatmay be similar in form and/or function to the processing circuitry 201,processor 205, memory 203 and device interface 207 described above.Specific structures, forms and scales of such components may differ.However, the general capabilities may be similar so these componentswill not be described in detail again in detail. Instead, it should beappreciated that except for changes in specific configuration, contentand structure, these components are generally similar. As shown in FIG.4, the user terminal 50 may further include a user interface 330 and anoperation manager 340.

The user interface 330 (if implemented) may be in communication with theprocessing circuitry 310 to receive an indication of a user input at theuser interface 330 and/or to provide an audible, visual, mechanical orother output to the user. As such, the user interface 330 may include,for example, a display (e.g., a touch screen display), one or morebuttons or keys (e.g., function buttons or a keyboard), and/or otherinput/output mechanisms (e.g., microphone, mouse, speakers, cursor,joystick, lights and/or the like). The user interface 330 may beconfigured to provide alerts, warnings and/or notifications to the useror operator responsive to various trigger conditions being detected(e.g., via the sensor equipment 30 or other components). Systemmalfunctions, damage or tampering with equipment, equipment theft andother component related stimuli may also be defined as triggers forgeneration of the alerts, warnings and/or notifications. In some cases,the user interface 330 may be configured to generate such alerts,warnings and/or notifications in response to the runtime or usage of thewatering pump 120 being out of the recommended ranges, or in response tosystem components having schedule or operational conflicts.Notifications may also be provided regarding general status, currentconditions and/or the like. The alerts, warnings and/or notificationsmay be generated via light, sound, visual display, or other devices thatmay be connected to or part of the operation manager 340. In some cases,the notifications may be provided by text message or email. Evenfurther, the user interface 330 may be configured to enable the user todelegate operation of the system to second user for a predeterminedperiod of time. For example, if the user is going on vacation or will beout of town, the second user may be given permission to control thesystem via the second user's user interface.

In an example embodiment, the processing circuitry 310 may be configuredto perform data processing, control function execution and/or otherprocessing and management services according to an example embodiment ofthe present invention. As such, it may be appreciated that theprocessing circuitry 310 may be configured to control or be embodied asthe operation manager 340. The operation manager 340 may be configuredto receive sensor information from the sensor equipment 30 and/or thewatering equipment 20 and make decisions regarding information to beprovided to the owner/operator and/or instructions to be provided to thesensor equipment 30 and/or the watering equipment 20. The processingcircuitry 310 may, in some cases, process the condition informationreceived from the sensor equipment 30 and compare the conditioninformation to growing condition parameters that are stored in thememory 314 for a given zone.

In an exemplary embodiment, the memory 314 may be configured to storeinformation, data, applications, instructions or the like for enablingthe operation manager 340 to carry out various functions in accordancewith exemplary embodiments of the present invention. For example, thememory 314 could be configured to buffer input data for processing bythe processor 312. Additionally or alternatively, the memory 314 couldbe configured to store instructions for execution by the processor 312.As yet another alternative, the memory 314 may include one or moredatabases that may store a variety of data sets responsive to input fromthe sensor network. Among the contents of the memory 314, applicationsmay be stored for execution by the processor 312 in order to carry outthe functionality associated with each respective application. In somecases, the applications may include applications for generation ofcontrol consoles for providing options for control of the system. Insome cases, the applications may also or alternatively includeapplications for receiving information regarding componentactivity/status, environmental parameters, operational or volume mode,device pairing, and/or the like to allow the operation manager 340 todefine responses to the information (e.g., based on predefinedprogramming or user input). The information/parameters may be entered bythe operator, received from deployed components, or may be extracted orretrieved from databases or sources accessible via the internet based onentry of an identity of the plant vegetation in a given zone.

The operation manager 340 may therefore, for example, provide interfacemechanisms for control of the operation of the watering pumps. FIG. 5illustrates a block diagram of one example of operations that may befacilitated by the operation manager 340 in accordance with an exampleembodiment. As shown in FIG. 5, the watering pump may initially be off,but the user terminal 50 may present a control console (or series ofcontrol consoles) via which the operator can provide instructions toinitiate the operations of FIG. 5. An instruction may be provided atoperation 400 to turn on the watering pump 120 (i.e., via selectingmanual mode). In response, a signal regarding the volume mode may bereceived at operation 401. Once, the pump on and volume mode signal isreceived, a determination may then be made at operation 402 as towhether the robotic rover 15 is active in the area (or at all). If therobotic rover 15 is active, a warning may be issued at the userinterface 330 of the user terminal 50 at operation 404. The operator maythen determine whether to allow operation of the watering pump 120 ornot at operation 406. If the operator decides not the operate thewatering pump 120, flow returns to the initial state. If the operatordecides to allow operation of the watering pump 120 anyway (e.g.,overriding or disregarding the warning), the operator may then be askedto enter a time duration for operation of the watering pump 120 atoperation 408. Of note, the operator may also have the option to cancelto return to the initial state at this time instead of entering the timeduration.

Assuming the time duration is entered, an activation signal may beissued from the user terminal 50 to the watering pump 120 to directoperation thereof at operation 410. The watering pump 120 may thenremain in an operating state until the time duration expires, at whichtime the watering pump 120 may turn off and flow returns to the initialstate. However, the operator may also insert instructions to manuallyturn off the watering pump 120 at operation 412. A determination maythen be made as to whether the manual turning off is before or overlapswith a scheduled start time at operation 414. If this manual turn off(off schedule) defines an end time that is before the scheduled nextstart time, the schedule may be maintained at operation 416 and thewatering pump 120 may turn off at operation 420 so that flow may returnto the initial state to be ready for operation again in accordance withthe schedule. However, if the manual shutoff corresponds with ascheduled start time, then the schedule may be skipped at operation 418and the watering pump 120 may turn off at operation 420 so that flow mayreturn to the initial state to be ready for operation again when thenext scheduled operating time arrives. Meanwhile, from the initialstate, if the scheduled operating time is reached at operation 422, thewatering pump 120 may operate at operation 410 at the correspondingtime, and responsive to time expiring at operation 424, the wateringpump 120 may shut off. Likewise, from the initial state, if an operationof the pump is triggered by sensor data at operation 426, the wateringpump 120 may operate at operation 410 and then shut off after apredetermined period of time expires at operation 424 or when thecondition clears at operation 428. Of note, the operator may alsomanually operates or shuts off the watering pump 120 by operating alocal button or knob at the watering pump 120. If manual (local)operation is performed, the operations described above may still beperformed and the times for remaining opening (or a next programmedopening) may again be governed by the schedule information input intothe operation manager 340.

In some cases, the watering pump 120 may include a limited userinterface in the form of a main button (or knob) provided on a frontpanel thereof, and a light assembly. The light assembly may includethree LEDs the LEDs may be capable of expressing red, green and yellowcolors in a solid or flashing manner. The LEDs may be useful forproviding status information associated with attempts to pair thewatering pump with another device, battery status, pump status, and/orthe like.

In an example embodiment, the user interface 330 of the user terminal 50may be employed initially to provide control console options for addingdevices to the first network so that they are discovered by the gateway40 and are recognized by the operation manager 340. When the pairingmode is initiated (e.g., by battery insertion into a deployed component,or by pressing the reset button, or by selection of an option on theuser terminal 50) for the watering pump, the watering pump may bediscovered by the gateway 40 and the gateway 40 may communicate theidentity of the discovered watering pump to the user operation manager340 so that information indicative of the discovered watering pump canbe displayed at the user interface 330. A determination is then made asto whether pairing is possible. The user interface 330 of the userterminal 50 may also or alternatively provide an indication of detectionof the watering pump. If the gateway 40 is unable to find the wateringpump, LED lighting output may be generated to indicate as much. Once thegateway 40 has discovered and is able to be paired with the wateringpump, the LED lighting outputs during the pairing mode may be convertedto a signal strength indicator. Again similar indications could also beprovided at the user terminal 50.

FIG. 6, which includes FIGS. 6A-6C, illustrates some examples ofinterface screens or control consoles that may be provided by theoperation manager 340 in some embodiments. FIG. 6A illustrates a basicstart screen showing a home page 600 for the app. The app may display ageneral watering pump data section 610, which may display runtime andusage data associated with watering pump 120. In some cases, the app mayalso display device status information 620, which may show each deviceof the first network along with corresponding status information suchas, for example, battery status, operational modes, operational status,and/or the like. In an example embodiment, an option may also beprovided for adding new devices in box 630. In some cases, an option maybe provided for delegated operation of the system to a second user inbox 640, as described above.

In some cases, by selecting the watering pump data section 610 (or anindividual sensor), various individual or collective screens showing thestatus of each sensor may be provided. FIG. 6B illustrates an examplepump status screen 650 that may be accessed responsive to selecting thewatering pump data section 610. In some embodiments, the pump statusscreen 650 may include a current pump data section 660 that may displaycurrent pump data. A historical pump data section 670 may also beprovided to show past data over a given period of time (that may be userselectable). A settings adjustment option 680 may also be provided toallow the operator to select various pump settings. The pump settingsmay relate to selecting operational or volume modes, pairing activity,signal strength, battery levels, identifying plant types nearby,identifying soil type and/or the like.

FIG. 6C illustrates an example device status screen 700 that may beaccessed responsive to selecting the adjust settings section 680. Insome embodiments, the user may be able to select what zone of the parcelthe user wishes to adjust the watering settings at section 710. Once theappropriate zone is selected, the user may be able to select theoperational and volume modes that the watering pump 120 is to operate inat sections 720 and 730, respectively. For example, if the user selectsintelligent mode in section 720, the user may then be prompted to selectthe appropriate volume mode from section 730. Even after selecting theintelligent operational mode in section 720, the user may then selecteither or both of the scheduled or manual modes in connection with thesame zone if the user desires. At section 740, the user may select thereset button in order to clear all currently stored operational andvolume mode settings.

Embodiments of the present invention may therefore be practiced usingone or more apparatuses such as the ones depicted in FIGS. 1-6. As such,a system of an example embodiment may include sensor equipment includingone or more sensors disposed on a parcel of land, watering equipmentdisposed on the parcel and configured to selectively apply water to theparcel, and a gateway configured to provide for communication with thesensor equipment and the watering equipment. The watering equipment mayinclude a watering pump operably coupled to a water source and a waterline to alternately couple the water source to and isolate the watersource from the water line, and processing circuitry. The processingcircuitry may be configured to receive instructions from the gateway;determine, based on the first instructions received from the gateway,the operational mode of the pump; and direct the pump to operate inaccordance with the operational mode.

In an example embodiment, the gateway may interface between a firstnetwork including at least the watering equipment and the sensorequipment and a second network via which a first user is enabled towirelessly communicate with the gateway via the user terminal. In somecases, the operational mode of the pump may include one of anintelligent mode, a scheduled mode, or a manual mode. Alternatively oradditionally, in the intelligent mode, the pump may operate in responseto received sensor data falling within or exceeding a predefined rangeor threshold. Alternatively or additionally, in the scheduled mode, thepump may operate in response to a watering schedule programmed by thefirst user. Alternatively or additionally, the user terminal may includean interface, and, where in the manual mode, the pump may operate inresponse to a user selection on the interface that directs the immediateoperation of the pump.

In further example embodiments, the processing circuitry may be furtherconfigured to determine, based on the first instructions received fromthe gateway, a volume mode of the pump. In some cases, the volume modeof the pump may include at least one of a micro drip mode, a smallamount mode, a conservation mode, an automatic mode, or a garden mode.Alternatively or additionally, the processing circuitry may be furtherconfigured to determine the recommended maintenance interval of thewatering pump. In some cases, the maintenance interval may be based on apredefined time period, water volume, or pump runtime. Alternatively oradditionally, the maintenance interval may be a calculated intervalbased on a last maintenance inputted by the first user. Alternatively oradditionally, the maintenance interval may be based on a time intervalor water volume inputted by the first user.

In further example embodiments, the processing circuitry (160) may befurther configured to detect a loss of connectivity to the gateway orthe sensor, and in response to the detection of the loss ofconnectivity, employ a last determined operational mode and volume mode.In some cases, if the loss of connectivity to the gateway (or the sensorexceeds a predetermined time interval), the processing circuitry may beconfigured to employ a default operational mode and volume mode. Infurther example embodiments, the user terminal may include an interfacedisplaying the status of the watering pump. Alternatively oradditionally, the user terminal may be configured to provide warnings tothe operator based on pump failure, battery status, schedule conflicts,and weather issues. Alternatively or additionally, the user terminal mayinclude an interface for delegating operation of the system to a seconduser selected by the first user.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe exemplary embodiments in the context of certainexemplary combinations of elements and/or functions, it should beappreciated that different combinations of elements and/or functions maybe provided by alternative embodiments without departing from the scopeof the appended claims. In this regard, for example, differentcombinations of elements and/or functions than those explicitlydescribed above are also contemplated as may be set forth in some of theappended claims. In cases where advantages, benefits or solutions toproblems are described herein, it should be appreciated that suchadvantages, benefits and/or solutions may be applicable to some exampleembodiments, but not necessarily all example embodiments. Thus, anyadvantages, benefits or solutions described herein should not be thoughtof as being critical, required or essential to all embodiments or tothat which is claimed herein. Although specific terms are employedherein, they are used in a generic and descriptive sense only and notfor purposes of limitation.

1. (canceled)
 2. A system comprising: sensor equipment comprising asensor disposed on a parcel of land; watering equipment configured toselectively apply water to the parcel of land, the watering equipmentcomprising a watering pump operably coupled to a water source and awater line to alternately couple the water source to and isolate thewater source from the water line; a user terminal comprising a userinterface, the user terminal being configured to display systeminformation based on sensor data received from the sensor; and a gatewayconfigured to communicate with the sensor equipment, the wateringequipment, and the user terminal; wherein the watering equipmentcomprises processing circuitry configured to: determine an operationalmode of the watering pump; and direct the watering pump to operate inaccordance with the operational mode; and wherein the user terminal isconfigured to delegate operational control of the system to a seconduser in response to a delegation input provided by a first user via theuser interface.
 3. The system of claim 1, wherein the user terminal isfurther configured to: receive, with the delegation input, a duration oftime for delegation of operational control of the system to the seconduser; enable operational control of the system by the second user duringthe duration of time; and disable operational control of the system bythe second user after the duration of time.
 4. The system of claim 1,wherein the user terminal is further configured to: receive, with thedelegation input, a date range for delegation of operational control ofthe system to the second user, the date range comprising a start dateand an end date; enable operational control of the system by the seconduser during the date range; and disable operational control of thesystem by the second user outside of the date range.
 5. The system ofclaim 1, wherein the user interface is configured to display a status ofthe watering pump, the status indicating the operational mode of thewatering pump.
 6. The system of claim 1, wherein the user interfacecomprises a touch screen display.
 7. The system of claim 1, wherein thesystem further comprises a second user terminal; wherein the userterminal is configured to delegate operational control of the system tothe second user to perform the operational control via the second userterminal.
 8. The system of claim 1, wherein the user terminal isconfigured to execute an app that provides an option for delegatingoperational control of the system to the second user.
 9. The system ofclaim 1, wherein the user terminal is configured to receive a delegateduser selection via the user interface indicating that the second userhas been selected to determine which user is to be delegated operationalcontrol.
 10. The system of claim 1 further comprising a second userterminal; wherein the second user terminal is configured to change theoperational mode of the watering pump in response to an input providedby the second user on the second user terminal when operational controlhas been delegated to the second user.
 11. The system of claim 9,wherein the second user terminal is configured to prevent a change tothe operational mode of the watering pump by the second user on thesecond user terminal when operational control has not been delegated tothe second user.
 12. The system of claim 9, wherein the operational modeof the watering pump is an intelligent mode; wherein, in the intelligentmode, the watering pump operates based upon a relationship between thesensor data and a threshold.
 13. A system comprising: a sensor disposedon a parcel of land, the sensor being configured to detect moistureconditions; watering equipment comprising a watering pump and processingcircuity, the processing circuitry being configured to direct thewatering pump to operate in accordance with an operational mode; and auser terminal comprising a user interface, the user terminal beingconfigured to: output system information via the user interface based onsensor data provided by the sensor, control the watering pump to operatein accordance with the operational mode; and delegate operationalcontrol of the system to a second user in response to a delegation inputprovided by a first user via the user interface.
 14. The system of claim12, wherein the user terminal is further configured to: receive, withthe delegation input, a duration of time for delegation of operationalcontrol of the system to the second user; enable operational control ofthe system by the second user during the duration of time; and disableoperational control of the system by the second user after the durationof time.
 15. The system of claim 12, wherein the user terminal isfurther configured to: receive, with the delegation input, a date rangefor delegation of operational control of the system to the second user,the date range comprising a start date and an end date; enableoperational control of the system by the second user during the daterange; and disable operational control of the system by the second useroutside of the date range.
 16. The system of claim 12, wherein the userinterface is configured to display a status of the watering pump, thestatus indicating the operational mode of the watering pump.
 17. Thesystem of claim 12, wherein the system further comprises a second userterminal; wherein the user terminal is configured to delegateoperational control of the system to the second user to perform theoperational control via the second user's user terminal.
 18. The systemof claim 12, wherein the user terminal is configured to execute an appthat provides an option for delegating operational control of the systemto the second user.
 19. The system of claim 12, wherein the userterminal is configured to receive a delegated user selection via theuser interface indicating that the second user has been selected todetermine which user is to be delegated operational control.
 20. Thesystem of claim 12 further comprising a second user terminal; whereinthe second user terminal is configured to change the operational mode ofthe watering pump in response to an input provided by the second user onthe second user terminal when operational control has been delegated tothe second user.
 21. The system of claim 19, wherein the second userterminal is configured to prevent a change to the operational mode ofthe watering pump by the second user on the second user terminal whenoperational control has not been delegated to the second user.